Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed fix for #275 #278

Merged
merged 1 commit into from
Feb 5, 2015
Merged

Proposed fix for #275 #278

merged 1 commit into from
Feb 5, 2015

Conversation

dlwyatt
Copy link
Member

@dlwyatt dlwyatt commented Feb 5, 2015

Both Mock -ModuleName, and InModuleScope, now share the same behavior with regard to module resolution:

  • The commands look specifically for Script modules. In order to work, there should be exactly one Script module with the given name loaded. If there is exactly one script module with the given name, any other non-script modules are ignored.
  • Under all other conditions, an appropriate error message is generated.

Both Mock -ModuleName, and InModuleScope, now share the same behavior with regard to module resolution:

- The commands look specifically for Script modules.  In order to work, there should be exactly one Script module with the given name loaded.  If there is exactly one script module with the given name, any other non-script modules are ignored.

- Under all other conditions, an appropriate error message is generated.
dlwyatt added a commit that referenced this pull request Feb 5, 2015
@dlwyatt dlwyatt merged commit 05b4594 into pester:master Feb 5, 2015
@dlwyatt dlwyatt deleted the MultiModuleFix branch February 5, 2015 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant